Skip to content

Change the scope for the netty client callback#886

Merged
tylerbenson merged 5 commits into
masterfrom
tyler/netty-client-callback
Jul 22, 2019
Merged

Change the scope for the netty client callback#886
tylerbenson merged 5 commits into
masterfrom
tyler/netty-client-callback

Conversation

@tylerbenson
Copy link
Copy Markdown
Contributor

@tylerbenson tylerbenson commented Jun 15, 2019

Previously the scope was the http client span, which could result in deep nesting. Now it is the parent span.

Before

[--------------Parent--------------]
  [ ^-----------Client------------]
               [ ^---Callback---]

Now:

[--------------Parent--------------]
  [ ^ --Client----] [ ^--Callback--]

Also improve the tests.

@tylerbenson tylerbenson added this to the 0.30.0 milestone Jun 15, 2019
@tylerbenson tylerbenson requested a review from mar-kolya June 15, 2019 00:21
@tylerbenson tylerbenson requested a review from a team as a code owner June 15, 2019 00:21
@tylerbenson tylerbenson force-pushed the tyler/netty-client-callback branch 2 times, most recently from a2181b1 to 9a8c8e2 Compare June 15, 2019 03:15
@labbati labbati modified the milestones: 0.30.0, 0.31.0 Jun 17, 2019
@tylerbenson tylerbenson force-pushed the tyler/netty-client-callback branch from 219168b to 6705a6d Compare June 17, 2019 23:44
@tylerbenson tylerbenson force-pushed the tyler/netty-client-callback branch from c2800e3 to 2e2cc97 Compare July 15, 2019 18:55
Copy link
Copy Markdown
Member

@labbati labbati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, please mark this PR as breaking change. I feel like we should be good to release it but still it changes the structure the user expects as of now

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question as above

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make sure, here the reasoning is instead of setting it explicitly I let HttpDecorator.onResponse() to do that!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case, I think we were previously setting the client span's status to error if the callback threw an error, which I don't think is correct.

@tylerbenson tylerbenson added the tag: breaking change Breaking changes label Jul 18, 2019
@tylerbenson
Copy link
Copy Markdown
Contributor Author

Let's figure out #917 first and apply the change to here before merging.

Previously the scope was the http client span, which could result in deep nesting.  Now it is the parent span.

Before
[——————Parent—————]
   [ ^ ———Client—————]
                        [ ^—Child—]

Now:
[——————Parent—————]
   [ ^ —Client—] [ ^—Child—]

Also improve the tests.
Adds reactive/circuitbreaker tests.
@tylerbenson tylerbenson force-pushed the tyler/netty-client-callback branch from 0063eba to ea4fc4a Compare July 19, 2019 16:27
@tylerbenson tylerbenson merged commit 7571b77 into master Jul 22, 2019
@tylerbenson tylerbenson deleted the tyler/netty-client-callback branch July 22, 2019 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tag: breaking change Breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants